home *** CD-ROM | disk | FTP | other *** search
- +==============================================================================+
- | |
- | Title: Modification to COMMAND.COM for DOS 3.10 to make ECHO OFF the |
- | default for BATCH file executions. |
- | |
- | Author: Gee M. Wong |
- | |
- | Date: 06/18/85 |
- | |
- | For months I have been searching for a patch for the DOS 3.10 version of |
- | COMMAND.COM which will make ECHO OFF the default initial state for BATCH |
- | file execution. Having not found anything, I decided to investigate this |
- | problem myself, and this is the solution I came up with. |
- | |
- | The following DEBUG session may be used to modify COMMAND.COM for DOS 3.10 |
- | to execute BATCH files with an initial default of ECHO OFF. |
- | |
- | >debug \command.com These debug commands will alter an |
- | -e 1967 0 AND AL,1 instruction into an AND AL,0. |
- | -w This one instruction chnage will force |
- | Writing 5AAA bytes ECHO OFF to be the default for BATCH |
- | -q file execution. |
- | |
- | Yes, it is actually that simple, and it works as advertised. However, |
- | there are two small problems: |
- | |
- | 1) ECHO ON will still be the default state during the initial |
- | execution of your AUTOEXEC.BAT file by the DOS boot. |
- | |
- | 2) If the last thing a BATCH file does is to set ECHO ON |
- | before terminating, then you will receive an extra DOS |
- | prompt. |
- | |
- | I have been working on this ECHO OFF problem for about a month now, and I |
- | have not found a solution, short of writing my own COMMAND.COM, to the |
- | problems mentioned above. And, as far as I know, there have been no ill |
- | effects introduced by this modification. |
- | |
- | |
- | Please, let me know if you encounter any problems. |
- | |
- | Gee M. Wong |
- | You can reach me on the Invention Factory bulletin board (212)-431-1194. |
- | |
- +==============================================================================+
-
- THE FOLLOWING MESSAGE WAS RECEIVED FROM BOB SMITH (THE AUTHOR OF
- 'TALL SCREEN') REGARDING THE DOS 3.1 ENVIRONMENT AREA. I HAVE
- TRIED THIS ON MY COPY OF DOS 3.1, AND IT SEEMS TO WORK PERFECTLY.
-
- RE EXPANDING THE PCDOS ENVIRONMENT AREA: A RECENT FORAGE INTO DOS 3.10'S
- COMMAND.COM UNCOVERED THE FOLLOWING SEEMINGLY SUPPORTED (BUT UNDOCUMENTED)
- FEATURE:
-
-
- /E:NN SET SIZE OF ENVIRONMENT AREA TO NN PARAGRAPHS.
- 10 ≤ NN ≤ 62 NUMBERS OUTSIDE THAT RANGE ARE IGNORED.
- THE DEFAULT IS /E:10.
-
-
- THIS FEATURE IS MOST USEFUL WHEN USED IN CONJUNCTION WITH THE SHELL= OPTION IN
- CONFIG.SYS. IN PARTICULAR, MY USAGE IS AS FOLLOWS:
-
- SHELL=C:\DOS\COMMAND.COM C:\DOS /P /E:20
-
-
- OTHER OPTIONS INCLUDE
-
- /D DON'T EXECUTE AUTOEXEC.BAT
-
- /F SKIP RESPONSE TO ABORT, RETRY, IGNORE QUESTION IN THE SYSTEM'S
- DEFAULT INT 24H HANDLER. QUITE LIKELY THIS FEATURE IS NAMED
- /F FOR FLAKY.
-
-
-
- A NOTE ON THE 'SHELL' COMMAND, ABOVE...
-
- THE SAMPLE 'SHELL=' CONFIG.SYS COMMAND, ABOVE, SHOWS SEVERAL UNDOCUMENTED
- OPTIONS AVAILABLE. IN PARTICULAR, THE FIRST PARAMETER SHOWS WHERE THE
- INITIAL COPY OF COMMAND.COM IS TO BE FOUND (IN THE ABOVE EXAMPLE, ON THE
- '/DOS' SUBDIRECTORY ON THE 'C:' DISK). THIS IS AS DOCUMENTED BY IBM.
-
-
- THE SECOND PARAMETER INDICATES THE DRIVE AND SUBDIRECTORY FROM WHICH
- COMMAND.COM IS TO BE RELOADED. HERE AGAIN, THE '/DOS' SUBDIRECTORY ON
- 'C:'.
-
-
- THE '/P' PARAMETER INDICATES THAT THE SUBSTITUTION SHOULD BE PERMANENT.
-
-
- NOTE THAT IN THE DOS 3.10 REFERENCE MANUAL, THE ABOVE TWO PARAMETERS
- ARE DESCRIBED FOR THE 'COMMAND' COMMAND. WHAT IBM DOESN'T TELL YOU IS
- THAT THEY ALSO WORK ON THE 'SHELL=' COMMAND IN CONFIG.SYS